--continue after Directory mv move - Migration Guide and Internal Mechanics explanation )This guide explains how to preserve Claude Code's --continue functionality when moving project directories, along with the underlying mechanics.
Note: Claude Code currently lacks built-in directory migration features. Each directory maintains independent conversation sessions, and history doesn't automatically transfer when projects are moved.
When you move a project directory and want to preserve your conversation history:
This gist will guide you through to setup starship along with zsh suggestions and zsh syntax highlight for your codespaces.
A pattern for building personal knowledge bases using LLMs.
This is an idea file, it is designed to be copy pasted to your own LLM Agent (e.g. OpenAI Codex, Claude Code, OpenCode / Pi, or etc.). Its goal is to communicate the high level idea, but your agent will build out the specifics in collaboration with you.
Most people's experience with LLMs and documents looks like RAG: you upload a collection of files, the LLM retrieves relevant chunks at query time, and generates an answer. This works, but the LLM is rediscovering knowledge from scratch on every question. There's no accumulation. Ask a subtle question that requires synthesizing five documents, and the LLM has to find and piece together the relevant fragments every time. Nothing is built up. NotebookLM, ChatGPT file uploads, and most RAG systems work this way.
| # AGENTS.md | |
| ## Engineering Philosophy | |
| This project values small, direct, understandable code. | |
| Prefer the simplest implementation that solves the problem without creating downstream complexity. Simple does not mean simplistic. It means the shortest clear path from point A to point B, with the fewest moving parts required to keep the system correct, maintainable, and easy to reason about. | |
| Avoid enterprise-style ceremony unless it is clearly justified by the problem. |